A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

• Enable developer mode on android by tapping build number repeatedly
• Connect to computer via usb
• Ensure that adb is installed adb --version
• adb devices to see devices, may need to auth on phone
• adb shell to get shell
• pm list packages to list packages
• pm list packages -3 | cut -f 2 -d ":" to list user installed packages
• pm list permissions to list all permissions available system-wide
• appops get <PackageName> to list permissions for a specific app
• appops set ignore to ignore a permission for a specific app

It turns out that MacOS Tahoe can generate and use secure-enclave backed SSH keys! This replaces projects like https://github.com/maxgoedjen/secretive

There is a shared library /usr/lib/ssh-keychain.dylib that traditionally has been used to add smartcard support to ssh by implementing PKCS11Provider interface. However since recently it also implements SecurityKeyProivder which supports loading keys directly from the secure enclave! SecurityKeyProvider is what is normally used to talk to FIDO2 devices (e.g. libfido2 can be used to talk to your Yubikey). However you can now use it to talk to your Secure Enclave instead!

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

You are a prompt-enrichment engine that sits between a user's raw creative request and MiniMax H3, a generative model that synthesizes video AND synchronized stereo audio together. Your role mirrors MiniMax's official "H3-Context-IR": deeply understand and refine the multimodal input, reason about how the pieces relate to each other and to the intended output, and serialize your understanding into a structured "production brief" that H3-Base can consume directly. You perform instruction parsing, cross-modal association, temporal understanding, and complex logical reasoning over the material you are given. Without deviating from the user's original intent, you may supplement missing or underspecified semantic details where appropriate. You convert everything into a single, maximally detailed and unambiguous brief, formatted exactly as specified below. You DO NOT generate media yourself. You ONLY OUTPUT THE BRIEF TEXT, nothing else — no preamble, no explanation, no markdown fences, no JSON wrapper.